Skip to content

feat(about): update Node.js release cycle information#8882

Open
matthewmayer wants to merge 1 commit into
nodejs:mainfrom
matthewmayer:patch-1
Open

feat(about): update Node.js release cycle information#8882
matthewmayer wants to merge 1 commit into
nodejs:mainfrom
matthewmayer:patch-1

Conversation

@matthewmayer
Copy link
Copy Markdown

Clarified the release status of odd and even Node.js versions and updated information on the release cycle starting with Node.js 27. While the change has not happened yet, would be good to list this on the releases page so developers who missed the announcement are aware of it in good time.

Description

Clarifies that the odd/even distinction will not happen in future.

Validation

Documentation update only

Related Issues

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run pnpm format to ensure the code follows the style guide.
  • I have run pnpm test to check if all tests are passing.
  • I have run pnpm build to check if the website builds without errors.
  • I've covered new added functionality with unit tests if necessary.

Clarified the release status of odd and even Node.js versions and updated information on the release cycle starting with Node.js 27.

Signed-off-by: Matt Mayer <152770+matthewmayer@users.noreply.github.com>
@matthewmayer matthewmayer requested a review from a team as a code owner May 7, 2026 16:34
@vercel
Copy link
Copy Markdown

vercel Bot commented May 7, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
nodejs-org Ready Ready Preview May 7, 2026 4:35pm

Request Review

@cursor
Copy link
Copy Markdown

cursor Bot commented May 7, 2026

PR Summary

Low Risk
Low risk documentation-only change; risk is limited to potential confusion if the stated future release policy changes.

Overview
Updates previous-releases.mdx to clarify that the odd/even release-line behavior applied historically through Node.js 26, and adds new guidance that starting with Node.js 27 the project will follow an annual cadence with each major moving from Current to Active LTS after six months.

Reviewed by Cursor Bugbot for commit ccdfa41. Bugbot is set up for automated code reviews on this repo. Configure here.

@avivkeller avivkeller changed the title content: Update Node.js release cycle information feat(about): update Node.js release cycle information May 16, 2026
Copy link
Copy Markdown
Member

@avivkeller avivkeller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @nodejs/release to make sure any other related info is updated

Major Node.js versions enter _Current_ release status for six months, which gives library authors time to add support for them.
After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to _Active LTS_ status and are ready for general use.
Historically (up to Node.js 26), odd-numbered releases (9, 11, etc.) become unsupported after six months, and even-numbered releases (10, 12, etc.) move to _Active LTS_ status and are ready for general use.
Starting with Node.js 27, the release cycle will be annual and every major version will move to _Active LTS_ status after its six-month _Current_ phase.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Starting with Node.js 27, the release cycle will be annual and every major version will move to _Active LTS_ status after its six-month _Current_ phase.
Starting with Node.js 27, the release cycle will be annual and every major version will move to _LTS_ status after its six-month _Current_ phase (and six additional months of _Alpha_ phase).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants